Skip to content

Conversation

aneta-petrova
Copy link
Member

What changes are you introducing?

This PR looks at the existing readmes and contribution documents and attempts to make it easier to navigate through them. As a result, there are now:

  • 3 readme files: one generic, one for guides/, one for web/, each with an introduction explaining their purpose (hinting at how they differ)
  • 1 contributing document, which now contains instructions for contributors and maintainers, including Foreman docs' own style guide
  • The Foreman docs minimalist style guide is new and is home to various pieces of markup and style conventions that were before located in different places.

One new thing that I'm adding is an explanation for the CP checklist in the PR template, to address #3219

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

To better separate types of information: readmes are for how to work with the repo; contributing is for how to contribute; style guide is for Foreman documentation conventions.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Hopefully the next step would be to review the style guide part to remove redundant information and duplicates. I found a few but I haven't really focused on that yet so if you spot something that could be dropped, I'd be happy to do so.

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.16/Katello 4.18 (Satellite 6.18)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4)
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • We do not accept PRs for Foreman older than 3.9.

Review checklists

Tech review (performed by an Engineer who did not author the PR; can be skipped if tech review is unnecessary):

  • The PR documents a recommended, user-friendly path.
  • The PR removes steps that have been made unnecessary or obsolete.
  • Any steps introduced or updated in the PR have been tested to confirm that they lead to the documented end result.

Style review (by a Technical Writer who did not author the PR):

  • The PR conforms with the team's style guidelines.
  • The PR introduces documentation that describes a user story rather than a product feature.

@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Sep 19, 2025
* [ ] I fill out the cherry-picking list in the PR template to the best of my abilities to signify which versions my update applies to.
If unsure, I let reviewers know so that they can assist.

## Foreman documentation minimalist style guide
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Potential reviewers: Note that all these style conventions have been moved from another document. I didn't write them and I'd like to avoid tweaking how they are worded 🙃 If anyone would like to see the wording improved, I'd suggest doing it in another PR. Thanks for understanding!

However, as noted in the PR description, I'd be happy to remove lines that are obsolete or redundant.

Copy link

github-actions bot commented Sep 19, 2025

The PR preview for 8d63fbc is available at theforeman-foreman-documentation-preview-pr-4281.surge.sh

No diff compared to the current base

show diff

Copy link
Contributor

@maximiliankolb maximiliankolb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some comments, overall LGTM!

@aneta-petrova aneta-petrova removed Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing labels Sep 22, 2025
@maximiliankolb maximiliankolb removed the Needs style review Requires a review from docs style/grammar perspective label Sep 22, 2025
@maximiliankolb maximiliankolb added the style review done No issues from docs style/grammar perspective label Sep 22, 2025
@aneta-petrova aneta-petrova merged commit 3051401 into theforeman:master Sep 22, 2025
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
style review done No issues from docs style/grammar perspective
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Review contribution guidelines for cherry-picking Consolidate and update "Contributing" docs (in progress)
2 participants